Systems and methods for modifying data usage permissions based on an event

ABSTRACT

A device receives instructions to update a field that defines a coverage area within a network. The device updates, based on receiving the instructions, the field to include a set of identifiers that are associated with a group of base stations within the coverage area. The device determines that a user equipment (UE), that is connected to the network, qualifies for the expanded data usage permissions based on account information associated with the UE including a particular identifier that allows the UE to utilize the expanded data usage permissions. The device provides, to another device, a request for data usage information that reflects the expanded data usage permissions. The device causes the data usage information to be applied to the UE.

BACKGROUND

A telecommunication provider may offer a service plan to a group ofcustomers. The service plan may indicate an amount of data that may beused throughout a payment period. In some cases, an event, such as anatural disaster, may cause undue hardship to individuals located in anarea of the natural disaster. In these cases, the telecommunicationprovider may offer free data to select customers, high-quality data toselect customers, high-speed data to select customers, and/or the like,regardless of the data plan utilized by those customers. For example, ifa natural disaster occurs, the telecommunication provider may offer freedata, high-quality data, high-speed data, and/or the like, to firstresponders that are performing one or more disaster-relief tasks in ornear a geographic area impacted by the natural disaster.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1F are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a diagram of an example functional architecture of an examplecore network described herein

FIG. 5 is diagram of an example environment in which systems, functionalarchitectures, and/or methods, described herein, may be implemented.

FIG. 6 is a flow chart of an example process for providing a userequipment (UE) that is within a coverage area with expanded data usagepermissions.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

In some situations, an event may occur which may cause undue hardship toindividuals located in a geographic area impacted by the event. In thesesituations, first responders may be dispatched to the geographic area toperform various disaster-relief tasks. If a first responder needs to usea network service to perform a task (e.g., making a phone call, usingthe Internet to look up a solution to a problem, and/or the like), anddoes not have data or minutes to perform the task, the first respondermay be unable to perform the task and/or may be delayed in performingthe task.

In some cases, telecommunication providers have been able to offerunrestricted data usage to select customers while an event is occurring.For example, if a natural disaster occurs, a telecommunication providermay be able to provide select first responders with the unrestricteddata usage. One technique may involve identifying a set of UEs that havebilling postal codes that are within a geographic area impacted by thenatural disaster and providing the set of UEs with the unrestricted datausage. However, this technique is unable to provide all first respondersin the geographic with unrestricted data usage. For example, if a teamof first responders are from a geographic area outside of an areaimpacted by the natural disaster, and are dispatched to the geographicarea impacted by the natural disaster, the technique would not be ableto provide the team of first responders with unrestricted data usagebecause each of the first responders would have accounts with billingpostal codes that are outside of the geographic area impacted by thenatural disaster.

Some implementations described herein provide a device (e.g., a mobilitymanagement entity (MME) or another type of network device) to perform aset of actions that provide a UE with expanded data usage permissionswhile connected to a network during a time of crisis. For example, anMME may be configured with a field (e.g., a presence reporting area(PRA) field, etc.) that defines a coverage area within a network. Whenan event occurs, the MME may receive instructions to update the fieldwith a set of identifiers that are associated with a group of basestations that are within a threshold distance of an area impacted by theevent. The set of identifiers may include a set of base stationidentifiers, a set of area tracking identifiers, and/or the like, andmay be used to define boundaries of the coverage area.

When the UE of a user (e.g., a first responder) enters the coveragearea, the UE may initiate a connection request to establish a connectionwith the network. When the MME receives the connection request (e.g.,from a base station), the MME may determine whether the UE qualifies forexpanded data usage permissions. For example, the MME and/or a policyand charging rules function (PCRF) device may determine whether the UEqualifies for the expanded data usage permissions based on accountinformation associated with the UE including a particular identifierthat grants the UE with the expanded data usage permissions (e.g., anidentifier indicating that the user is a first responder). If the UEqualifies for the expanded data usage permissions, the MME may interactwith another network device (e.g., the PCRF device, etc.) to obtain datausage information that reflects the expanded data usage permissions. Thedata usage information may be used to provide the UE with an increase ina quantity of data available to the user (e.g., relative to the user'sdata plan), may provide access to data free of cost, may influence oneor more quality of service (QoS) parameters to improve a quality of aconnection to the network, may lift data throttling limitations, and/orthe like. Additionally, the UE may interact with a serving base stationto cause the data usage information to be applied to a sessionassociated with the UE.

In this way, the MME identifies that the UE is to be given access to theexpanded data usage permissions while the UE is within the coveragearea. Additionally, by providing the UE with access to expanded datausage permissions, the user may be able to use one or more data servicesduring a time of crisis or hardship. This could assist a first responderin saving human lives, allow the first responder to completedisaster-relief tasks more efficiently and effectively (thereby allowingthe first responder to help more individuals during key moments of acrisis), and/or the like.

Furthermore, the MME conserves resources (e.g., processing resources,network resources, memory resources, and/or the like) by providing theUE with access to the expanded data usage permissions. For example,without access to the expanded data usage permissions, a user in an areaimpacted by an event may waste resources repeatedly making failedattempts to connect to the network, may waste resources by calling atelecommunication provider to inquire about receiving access toadditional data usage, may waste resources by utilizing a slow networkconnection (e.g., which utilizes UE resources and network resources,while likely being too slow to help the user), and/or the like.

Additionally, the process described herein may be automated, which mayremove human subjectivity and waste from the process, and which improvesspeed and efficiency of the process and conserve computing resources(e.g., processor resources, memory resources, and/or the like). Forexample, the MME (and/or one or more other devices described herein)may, without human intervention, automatically provide particular UEswith access to expanded data usage permissions. This eliminates a needfor a network administrator to manually interact with a device toprovide the particular UEs with the access to the expanded data usagepermissions, thereby conserving resources of the device, reducing oreliminating chances of human error, and improving quality and efficiencyof the process. Additionally, implementations described herein use arigorous, computerized process to perform tasks or roles that were notpreviously performed or were previously performed using subjective humanintuition or input.

FIGS. 1A-1F are diagrams of one or more example implementations 100described herein. Example implementation(s) 100 may include a group ofmobility management entities (MMEs) 102 (shown as MME 102-1, . . . , MME102-N), a home subscriber server/subscriber data manager (HSS/SDM) 104,two user equipment (UE) 106 (referred to collectively as UEs 106 or UE106-1 and UE 106-2, respectively), a base station 108, a serving gateway(SGW) 110, a packet data network gateway (PGW) 112, and a policy andcharging rules function (PCRF) 114. One or more of these devices maycommunication via a network, such as a fifth generation (5G) network, afourth generation (4G) long-term evolution (LTE) network, and/or asimilar type of network. As shown in FIGS. 1A-1F, MME 102-1 may performa set of actions to provide UEs 106 with expanded data usage permissionswithin the coverage area.

As shown in FIG. 1A, and by reference number 116, the group of MMEs 102may be configured with a field that can include values that define acoverage area. For example, the group of MMEs 102 may be configured witha presence reporting area (PRA) field that may be populated with a setof identifiers that define a coverage area. In some cases, the set ofidentifiers may include a set of base station identifiers, a set of areatracking identifiers (e.g., a set of tracking area codes (TACs), a setof tracking area identities (TAIs)), and/or the like.

In some implementations, the set of identifiers may be used to definegeographic boundaries of the coverage area (e.g., the set of identifiersmay correspond to base stations that are each assigned a geographic areaof coverage within the network). As an example, if the PRA field isupdated to include a set of base station identifiers for a set of basestations, and each base station is assigned a geographic area ofcoverage, a total geographic area of coverage for the set of basestations may serve as the coverage area.

In some cases, MMEs 102 may configure a set of fields. For example,rather than have one PRA field that may include a set of identifiers,MMEs 102 might be configured such that a set of fields corresponds tothe set of identifiers.

As shown by reference number 118, HSS/SDM 104 may configure accountinformation associated with a group of UEs (e.g., a group of UEs thatinclude UEs 106) with a particular identifier that serves as anindicator that the group of UEs are eligible for receiving expanded datausage permissions, as described further herein. The particularidentifier may be represented by a value, a flag, a message, an absenceof a value or flag or message, and/or the like. The particularidentifier may be associated with a particular UE, associated with aparticular user, associated with an account, and/or the like. The groupof UEs may be accessible to users may be a group of users who have beenidentified as eligible to take advantage of expanded data usagepermissions within the coverage area, such as a group of firstresponders, a group of individuals affected by events such as naturaldisasters, and/or the like.

As an example, to identify first responders, a telecommunicationprovider may interact with one or more public safety departments toidentify a list of subscriber profiles that are first responders. Inthis case, HSS/SDM 104 may configure the subscriber profile information,for users included in the list, to include the particular identifiers.This may allow UEs 106 associated with the first responders to be markedas being eligible for expanded data usage permissions, as describedfurther herein.

In this way, the group of MMEs 102 may be configured with the field thatcan be used to define the coverage area and HSS/SDM 104 may configurethe subscriber profiles with the particular identifier that indicateswhich users are eligible for expanded data usage permissions within thecoverage area.

As shown in FIG. 1B, and by reference number 120, UE 106-1 may provide aconnection request (e.g., an attachment request) to base station 108.For example, UE 106-1 may enter an area of coverage of base station 108and may provide a connection request to base station 108 based on UE106-1 powering on, returning from an idle state, enabling a networkconnection feature, moving into range of base station 108, and/or thelike. The connection request may include device information of UE 106-1,such as a device identifier (e.g., an international mobile equipmentidentity (IMEI) number, an international mobile subscriber identity(IMSI) number, a mobile subscriber mobile station international (MSISDN)number, a unique device identifier (UDID), etc.) and/or otherinformation that may be used to establish a connection with the network.

As shown by reference number 122, base station 108 may provide theconnection request to MME 102-1. As shown by reference number 124, MME102-1 may provide the connection request to PCRF 114. For example, MME102-1 may provide the connection request to SGW 110, which may providethe connection request to PGW 112, which may provide the connectionrequest to PCRF 114. As shown by reference number 126, PCRF 114 mayobtain subscriber profile information for a user associated with UE106-1. In some cases, PCRF 114 may analyze the subscriber profileinformation to determine that the subscriber profile informationincludes a particular identifier (e.g., an identifier assigned to asubscriber profile of a first responder). Additionally, PCRF 114 mayinclude the particular identifier as part of a connection response.

As shown by reference number 128, PCRF 114 may provide, to MME 102-1,the connection response that includes the device identifier and/or theparticular identifier. For example, PCRF 114 may provide the connectionresponse to PGW 112, which may provide the connection response to SGW110, which may provide the connection response to MME 102-1.

As shown by reference number 130, MME 102-1 may determine whether thecoverage area is active and/or may determine whether UE 106-1 qualifiesfor expanded data usage permissions. For example, MME 102-1 maydetermine whether the coverage area is active by analyzing the field todetermine whether the field includes identifiers associated withparticular base stations. In the example shown, MME 102-1 may analyzethe field to determine that the field includes null values (or novalues). The null values (or lack of identifier values) may be anindicator that coverage area is not active (e.g., because an event, suchas a natural disaster, has not occurred, and thus the coverage area hasyet to be activated).

In some implementations, MME 102-1 may determine whether UE 106-1qualifies for the expanded data usage permissions. For example, MME102-1 may analyze contents of the connection response, and may determinethat UE 106-1 qualifies for the expanded data usage permissions based onthe connection response including the particular identifier.

Expanded data usage permissions, as used herein, may refer to expandeddata usage permissions relative to a data plan of a user associated witha UE (e.g., UE 106-1, UE 106-2, etc.). The data usage permissions may beexpanded by modifying data usage information that influences access todata while the UE is connected to the network, charges for data usage,availability of particular quality of service (QoS) features, and/or thelike. Data usage information, as used herein, may include informationindicating a quantity of data that may be provided to the UE,information indicating an amount of data that may be provided free ofcost, information indicating to remove one or more data restrictionsthat may be applicable to the UE (e.g., information indicating to removeone or more data throttling restrictions, such that data usage of asession is not restricted to a particular speed or a particularbandwidth), information indicating to modify one or more QoS parametersthat affect the quality of the UE's connection (e.g., such as byincreasing an amount of bandwidth available to the UE, removing arestriction on the amount of bandwidth available to the UE, etc.),and/or the like.

In some implementations, MME 102-1 may update a data structure to storea record indicating that UE 106-1 qualifies for the expanded data usagepermissions. The data structure may, for example, associate a deviceidentifier of UE 106-1 and the particular identifier. This may allow MME102-1 to keep a local record that indicates that UE 106-1 qualifies forthe expanded data usage permissions. The local record may be kept forall (or some) UEs that are presently connected to the network via MME102-1. In this way, if the coverage area is activated while one or moreof the UEs are still connected to the network, MME 102-1 may be able toimmediately interact with one or more network devices (e.g., PCRF 114,etc.) to request that the UEs be given the expanded data usagepermissions, as described further herein.

As shown by reference number 132, MME 102-1 may provide the connectionresponse to base station 108. As shown by reference number 134, basestation 108 may provide the connection response to UE 106-1.

In this way, and as shown by reference number 136, UE 106-1 is able toconnect to the network with expected data usage permissions (e.g., asindicated in the data plan of the user).

As shown in FIG. 1C, and by reference number 138, MME 102-1 may receiveinstructions to update the field (e.g., the PRA field) that defines thecoverage area within the network. For example, an event may occur thatcauses an authorized user of a telecommunication provider to generateand provide MME 102-1 with instructions to update the field. Theinstructions may include, for example, a set of identifiers that may beused to define a set of geographic boundaries of the coverage area. Forexample, the set of identifiers may be associated with a set of basestations that each have a pre-determined area of coverage. In this case,the set of identifiers may be used to define a geographic area that isequal to the area of coverage of the set of base stations. The set ofidentifiers may include a set of base station identifiers, a set of areatracking identifiers that correspond to areas serviced by particularbase stations (e.g., a set of TACs, a set of TAIs, etc.), and/or thelike.

In some implementations, the instructions may be provided to MME 102-1based on an event. An event, as used herein, may refer to an act,situation, and/or the like, that causes undue hardship to a class ofusers, which may create a need for data services in an area impacted bythe event. The event may be a natural disaster, a power outage, asituation where one or more network devices of a service area havereached maximum capacity (e.g., if too many users are on the network ina particular area, connections may be slowed, and first responders orother important individuals may be unable to access data services),and/or the like.

As an example, one or more managers that work for a telecommunicationprovider may identify that an event is occurring and may determine thatan area impacted by the event may need to be a coverage area. In thisexample, the one or more managers may give an authorized user (e.g., anetwork administrator) permission to generate and provide MME 102-1 withinstructions to update the field that defines the coverage area.

While the example described here provides one MME (e.g., MME 102-1)receiving the instructions, in practice, the coverage area may extend toa geographic region that is serviced by multiple MMES 102 (e.g., inwhich case the instructions may be provided to each of the MMES 102).

As shown by reference number 140, MME 102-1 may update the field. Forexample, MME 102-1 may update the field (e.g., the PRA field) based onreceiving the instructions. In this case, MME 102-1 may process theinstructions to identify the set of identifiers and may include the setof identifiers as values within the field.

As shown by reference number 142, MME 102-1 may determine that UE 106-1qualifies for the expanded data usage permissions. For example, MME102-1 may have determined that UE 106-1 qualifies for the expanded datausage permissions when UE 106-1 initially connected to the network. Assuch, MME 102-1 may simply reference the data structure described aboveto determine that the device identifier associated with UE 106-1 isstored in association with the particular identifier that indicates thata user associated with UE 106-1 is eligible for the expanded data usagepermissions.

In some implementations, MME 102-1 (or another network device) mayautomatically update the field. For example, if a national weatherservice issues a weather warning for an area (e.g., a hurricane, atornado, a wildfire, and/or the like), MME 102-1 (or the other networkdevice) may receive data identifying the weather warning. As an example,MME 102-1 may receive the data based on subscribing to be a recipientthat is to be automatically provided weather warnings, may obtain thedata based on analyzing a website or data source that broadcasts theweather warning, and/or the like. Additionally, MME 102-1 may analyzethe data identifying the weather warning to determine whether to updatethe field. For example, MME 102-1 may determine a degree of severity ofthe weather warning by analyzing the data using one or more naturallanguage processing techniques and may determine whether to update thefield based on whether a value representing the degree of severity ofthe weather warning satisfies a threshold value. In this way, MME 102-1may update the field without receiving the instructions from a deviceoperated by a human user.

In some implementations, MME 102-1 may not store a local record thatindicates that UE 106-1 qualifies for the expanded data usagepermissions. For example, MME 102-1 may provide a request to PCRF 114for an indication of whether UE 106-1 qualifies for the expanded datausage permissions. In this case, PCRF 114 may obtain the subscriberprofile information for the user associated with UE 106-1 to determinewhether the subscriber profile information includes the particularidentifier (e.g., the identifier assigned to a subscriber profile of afirst responder). Additionally, PCRF 114 may provide a message to MME102-1 indicating that UE 106-1 qualifies for the expanded data usagepermissions.

As shown by reference number 144, MME 102-1 may provide a request (e.g.,a modify bearer request) to PCRF 114. For example, MME 102-1 may providea modify bearer request to PGW 110, SGW 110 may provide the modifybearer request to PGW 112, and PGW 112 may provide the modify bearerrequest to PCRF 114. The modify bearer request may include the deviceidentifier, the particular identifier, an indication that UE 106-1qualifies for the expanded data usage permissions, a request for thedata usage information that reflects the expanded data usagepermissions, and/or the like.

As shown by reference number 146, PCRF 114 may identify the data usageinformation that reflects the expanded data usage permissions. Forexample, PCRF 114 may be configured with the data usage information thatreflects the expanded data usage permissions, and may, upon receivingthe request, identify the data usage information that is to be offeredto UE 106-1.

As shown by reference number 148, PCRF 114 may provide, to MME 102-1, aresponse (e.g., a modify bearer response) that includes the data usageinformation that has been identified. For example, PCRF 114 may providethe modify bearer response to PGW 112, PGW 112 may provide the modifybearer response to SGW 110, and SGW 110 may provide the modify bearerresponse to MME 102-1. As shown by reference number 150, MME 102-1 mayprovide the response to base station 108, and, as shown by referencenumber 152, base station 108 may provide the response to UE 106-1.

In this way, and as shown by reference number 154, UE 106-1 may beconnected to the network in a manner that utilizes the data usageinformation that reflects the expanded data usage permissions. Toprovide an example, if UE 106-1 had a data plan that allows for twogigabytes (GB) a month of data use, and UE 106-1 had already used alltwo GB of the data, UE 106-1 may be unable to access data services in anarea impacted by the event (e.g., unless a Wi-Fi hotspot was availableand in a vicinity of UE 106-1). However, after receiving the responsefrom base station 108, UE 106-1 may have been effectively switched to anunlimited data plan, such that the user may use UE 106-1 for dataservices, despite having previously used all available data that wasprovided as part of the user's data plan.

FIGS. 1D and 1E show an example process of a second UE (UE 106-2) thatqualifies for the expanded data usage permissions but that connects tothe network after the coverage area has been activated (whereas UE 106-1had connected to the network prior to the coverage area beingactivated).

As shown in FIG. 1D, and by reference number 156, UE 106-2 may provide aconnection request (e.g., an attachment request) to base station 108. Asindicated above, the connection request may be provided after thecoverage area has been activated. The connection request may include adevice identifier of UE 106-2.

As shown by reference number 158, base station 108 may provide theconnection request to MME 102-1. In some implementations, despite thatUE 106-2 is attempting to initiate a connection to the network, MME102-1 may reference the data structure to determine whether UE 106-2qualifies for the expanded data usage permissions. For example, MME102-1 may save values stored via the data structure for a threshold timeperiod after particular UEs 106 disconnect from the network, such thatif a particular UE 106 reconnects to the network within the thresholdtime period, MME 102-1 will still have a local record to reference thatindicates whether the particular UE 106 qualifies for the expanded datausage permissions.

As shown by reference number 160, MME 102-1 may provide the connectionrequest to PCRF 114. For example, MME 102-2 may provide the connectionrequest to SGW 110, SGW 110 may provide the connection request to PGW112, and PGW 112 may provide the connection request to PCRF 114. Asshown by reference number 162, PCRF 114 may obtain, from HSS/SDM 104,the account information that includes a particular indicator (e.g., anidentifier indicating that a user associated with UE 106-2 is a firstresponder and thus qualifies for the expanded data usage permissions).As shown by reference number 164, PCRF 114 may provide, to MME 102-1, aconnection response that includes the particular identifier. Forexample, PCRF 114 may provide the connection response to PGW 112, PGW112 may provide the connection response to SGW 110, and SGW 110 mayprovide the connection response to MME 102-1.

As shown by reference number 166, MME 102-1 may determine whether thecoverage area is active and/or whether UE 106-2 qualifies for theexpanded data usage permissions. For example, MME 102-1 may determinethat the coverage area is active in a manner described elsewhere herein(e.g., by analyzing values of the field that defines the coverage area).Additionally, MME 102-1 may determine that UE 106-2 qualifies for theexpanded data usage permissions in a manner described elsewhere herein(e.g., based on the connection response including the particularidentifier). In some implementations, MME 102-1 may update the datastructure to associate the device identifier of UE 106-2 and theparticular identifier, in a manner similar to that described elsewhereherein.

In this way, MME 102-1 is able determine that UE 106-2 qualifies for theexpanded data usage permissions, even when UE 106-2 connects to thenetwork after the coverage area is activated.

As shown in FIG. 1E, and by reference number 168, MME 102-1 may provide,to PCRF 114, a request (e.g., a modify bearer request) for the datausage information that reflects the expanded data usage permissions. Asshown by reference number 170, PCRF 114 may identify the data usageinformation that reflects the expanded data usage permissions, asfurther described elsewhere herein. As shown by reference number 172,PCRF 114 may provide, to MME 102-1, a response (e.g., a modify bearerresponse) that includes the data usage information.

In some implementations, as shown above, MME 102-1 may provide twoseparate requests (e.g., the connection request described in connectionwith reference number 160 and the modify bearer request described inconnection with reference number 168). This is because MME 102-1 doesnot know whether UE 106-2 is eligible for the expanded data usagepermissions at the time that UE 106-2 provides the connection request.In some implementations, rather than provide two separate requests, MME102-1 may provide, with the connection request, conditional instructionsthat could cause PCRF 114 to provide the data usage information with theconnection response (e.g., instead of having to send a separate modifybearer request, as showed in connection with reference number 168). Theconditional instructions may, for example, be conditioned upon PCRF 114verifying that the subscriber profile information for the userassociated with UE 106-2 includes the particular identifier. Thisconserves resources (e.g., processing resources, network resources,memory resources, and/or the like) by eliminating a need to send twoseparate requests.

As shown by reference number 174, MME 102-1 may provide base station 108with the response (e.g., the modify bearer response). For example, theresponse may be provided using a protocol associated with an evolvedpacket system, such as by using a non-access stratum (NAS) protocol tosend a downlink NAS message. As shown by reference number 176, basestation 108 may provide UE 106-2 with the response. For example, theresponse may be provided as part of a reconfiguration message using aradio resource control (RRC) protocol.

In this way, and as shown by reference number 178, UE 106-2 may beconnected to the network in a manner that utilizes the data usageinformation that reflects the expanded data usage permissions.

As shown in FIG. 1F, MME 102-1 may perform one or more actions thatcause sessions (e.g., data sessions) utilized by UE 106-1 and UE 106-2to be limited by the expected data usage permissions (e.g., data usagepermissions identified in data plans of each respective user). Forexample, and as shown by reference number 180, MME 102-1 may receiveinstructions to reset at least one of the one or more fields that definethe coverage area. The instructions may be provided to MME 102-1 whenthe coverage area is no longer needed, when a portion of the coveragearea is no longer needed, and/or the like. In these cases, theinstructions may indicate to reset the entire field (e.g., by clearingthe set of indicators represented as values within the field), to resetsome of the values included within the field (e.g., by clearing a subsetof the set of indicators), and/or the like.

In some implementations, the instructions may be provided to MME 102-1from a device associated with an authorized user. For example, after anatural disaster occurs, and first responders have completeddisaster-relief tasks, a network administrator of a telecommunicationprovider may provide MME 102-1 with instructions indicating to resetvalues included in the field. As another example, MME 102-1 mayautomatically reset the field. For example, if the national weatherservice issues a broadcast that there is no longer a weather warning foran area, MME 102-1 (or another network device) may, upon receiving dataidentifying the contents of the broadcast, analyze the contents todetermine to reset the field.

As shown by reference number 182, MME 102-1 may reset the field. Forexample, MME 102-1 may reset a PRA field by removing at least a portionof the set of indicators associated with the set of base stations fromthe PRA field. Resetting a field may refer to deleting the indicatorvalue from memory, replacing the indicator value with a null value,and/or the like.

As shown by reference number 184, MME 102-1 may provide one or morerequests (e.g., one or more modify bearer requests) for particular datausage information that reflect the expected data usage permissions of UE106-1 and UE 106-2. For example, MME 102-1 may provide the one or morerequests to SGW 110, SGW 110 may provide the one or more requests to PGW112, and PGW 112 may provide the one or more requests to PCRF 114. Asmentioned elsewhere herein, the expected data usage permissions mayrefer to data usage permissions indicated by a data plan of a particularuser. The request may include one or more device identifiers (e.g., adevice identifier of UE 106-1 and/or a device identifier of UE 106-2)that one or more other network devices (e.g., PCRF 114, HSS/SDM 104,etc.) may use to look up the expected data usage permissions of eachrespective user, as described below.

In some cases, MME 102-1 may provide a separate request for each UE 106(e.g., a first request for UE 106-1, a second request for UE 106-2,etc.). In other cases, MME 102-1 may provide a single request formultiple UEs 106 (e.g., a request for particular data usage informationfor both UE 106-1 and UE 106-2).

As shown by reference number 186, PCRF 114 may identify the particulardata usage information that reflects the expected data usagepermissions. For example, PCRF 114 may identify the identify theparticular data usage information that reflects the expected data usagepermissions, such that a quantity of data, a limit to a quantity ofdata, a bandwidth range, and/or the like, that is being offered to theUEs 106 may be replaced by values indicated by data plans of the users.In this case, PCRF 114 may use the one or more device identifiersincluded in the request to look up the subscriber profile informationfor each respective user, which may include the expected data usagepermissions as indicated by each respective user's data plan.

As shown by reference number 188, PCRF 114 may provide, to MME 102-1,one or more responses (e.g., one or more modify bearer responses) thatinclude the particular data usage information. For example, PCRF 114 mayprovide the one or more requests to PGW 112, PGW 112 may provide the oneor more requests to SGW 110, and SGW 110 may provide the one or morerequests to MME 102-1. As shown by reference number 190, MME 102-1 mayprovide the one or more responses to base station 108 (i.e., the servingbase station). For example, the one or more responses may be providedusing a protocol associated with an evolved packet system, such as byusing a NAS protocol to send a downlink NAS message. As shown byreference number 192, base station 108 may provide the one or moreresponses to each respective UE 106. For example, the one or moreresponses may be provided as part of a reconfiguration message using aradio resource control (RRC) protocol.

As shown by reference number 194, UEs 106 may be connected to thenetwork in a manner that utilizes the particular data usage information.As such, the sessions that are active may now be restricted based on atype of data plan used by the users, based on a current amount ofavailable data that the users have remaining in a particular billingcycle, and/or the like. In this way, users, such as first responders,are able to use their data plans when the coverage area is inactive andare able to take advantage of the expanded data usage permissions whenthe coverage area is active.

In some implementations, MME 102-1 may add new indicators to the field.For example, MME 102-1 may receive instructions to add new indicators asvalues of the field to increase a geographic area covered by thecoverage area.

In some implementations, UE 106-1 or UE 106-2 may move from a servicearea covered by a first base station 108 (e.g., a serving base station108) to a service area covered by a second base station 108 (e.g., atarget base station). In this case, the first base station 108 mayinteract with the second base station 108 (referred to as a target basestation 108) to perform a handover procedure, such that the second basestation 108 is able to become a new serving base station 108. During (orbefore) the handover procedure, the first base station 108 may interactwith MME 102-1 to determine whether the second base station 108 iswithin the coverage area. If not, MME 102-1 may perform one or moreactions described elsewhere herein to ensure that, after the handoverprocedure is completed, that UE 106-1 or UE 106-2 are to be connected tothe network in a manner that utilizes particular data usage informationthat corresponds to the expected data usage permissions.

In this way, MME 102-1 is able to identify that UEs 106 are to be givenaccess to the expanded data usage permissions while the UEs 106 arewithin the coverage area. Additionally, by providing the UEs 106 withaccess to expanded data usage permissions, respective users of the UEs106 may be able to use one or more data services during a time of crisisor hardship. This could assist a user in saving human lives, allow theuser to complete disaster-relief tasks more efficiently and effectively(thereby allowing the user to help more individuals during key momentsof a crisis), and/or the like.

Furthermore, MME 102-1 conserves resources (e.g., processing resources,network resources, memory resources, and/or the like) by providing theUEs 106 with access to the expanded data usage permissions. For example,without access to the expanded data usage permissions, a user in an areaimpacted by the event may waste resources repeatedly making failedattempts to connect to the network, may waste resources by calling atelecommunication provider to inquire about receiving access toadditional data usage, may waste resources by utilizing a slow networkconnection (e.g., which may utilize resources of a particular UE 106and/or network resources, while likely being too slow to help the user),and/or the like.

As indicated above, FIGS. 1A-1F are provided merely as an example. Otherexamples may differ from what was described with regard to FIGS. 1A-1F.For example, there may be additional devices and/or networks, fewerdevices and/or networks, different devices and/or networks, ordifferently arranged devices and/or networks than those shown in FIGS.1A-1F. Furthermore, two or more devices shown in FIGS. 1A-1F may beimplemented within a single device, or a single device shown in FIGS.1A-1F may be implemented as multiple and/or distributed devices.Additionally, or alternatively, a set of devices (e.g., one or moredevices) of example implementation(s) 100 may perform one or morefunctions described as being performed by another set of devices ofexample implementation(s) 100.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user equipment (UE) 205, a base station210, a mobility management entity (MME) 215, a serving gateway (SGW)220, a packet data network gateway (PGW) 225, a policy and chargingrules function (PCRF) 230, a home subscriber server/subscriber datamanager (HSS/SDM) 235, an authentication, authorization, and accountingserver (AAA) 240, and/or a network 245. Devices of environment 200 mayinterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

Some implementations are described herein as being performed within along-term evolution (LTE) network for explanatory purposes. Someimplementations may be performed within a network that is not an LTEnetwork, such as a fifth generation (5G) network or a third generation(3G) network.

Environment 200 may include an evolved packet system (EPS) that includesan LTE network and/or an evolved packet core (EPC) that operate based ona third-generation partnership project (3GPP) wireless communicationstandard. The LTE network may include a radio access network (RAN) thatincludes one or more base stations 210 that take the form of evolvedNode Bs (eNBs) via which UE 205 communicates with the EPC. The EPC mayinclude MME 215, SGW 220, and/or PGW 225 that enable UE 205 tocommunicate with network 245 and/or an Internet protocol (IP) multimediasubsystem (IMS) core. The IMS core may include HSS/SDM 235 and/or AAA240, and may manage device registration and authentication, sessioninitiation, etc., associated with UE 205. HSS/SDM 235 and/or AAA 240 mayreside in the EPC and/or the IMS core.

UE 205 includes one or more devices capable of communicating with basestation 210 and/or a network (e.g., network 245, etc.). For example, UE205 may include a wireless communication device, a radiotelephone, apersonal communications system (PCS) terminal (e.g., that may combine acellular radiotelephone with data processing and data communicationscapabilities), a smart phone, a laptop computer, a tablet computer, apersonal gaming system, user equipment, and/or a similar device. UE 205may be capable of communicating using uplink (e.g., UE to base station)communications, downlink (e.g., base station to UE) communications,and/or side link (e.g., UE-to-UE) communications. In someimplementations, UE 205 may include a machine-type communication (MTC)UE, such as an evolved or enhanced MTC (eMTC) UE. In someimplementations, UE 205 may include an Internet of Things (IoT) UE, suchas a narrowband IoT (NB-IoT) UE and/or the like.

In some implementations, UE 205 may provide a connection request (e.g.,an attachment request) to base station 210. In some implementations, UE205 may receive a connection response (e.g., an attachment response)from base station 210. In some implementations, UE 205 may receive aresponse (e.g., a modify bearer response) from base station 210.

Base station 210 includes one or more devices capable of communicatingwith UE 205 using a cellular Radio Access Technology (RAT). For example,base station 210 may include a base transceiver station, a radio basestation, a node B, an evolved node B (eNB), a gNB, a base stationsubsystem, a cellular site, a cellular tower (e.g., a cell phone tower,a mobile phone tower, etc.), an access point, a transmit receive point(TRP), a radio access node, a macrocell base station, a microcell basestation, a picocell base station, a femtocell base station, or a similartype of device. Base station 210 may transfer traffic between UE 205(e.g., using a cellular RAT), other base stations 210 (e.g., using awireless interface or a backhaul interface, such as a wired backhaulinterface), and/or network 245. Base station 210 may provide one or morecells that cover geographic areas. Some base stations 210 may be mobilebase stations. Some base stations 210 may be capable of communicatingusing multiple RATs.

In some implementations, base station 210 may perform scheduling and/orresource management for UEs 205 covered by base station 210 (e.g., UEs205 covered by a cell provided by base station 210). In someimplementations, base stations 210 may be controlled or coordinated by anetwork controller, which may perform load balancing, network-levelconfiguration, and/or the like. The network controller may communicatewith base stations 210 via a wireless or wireline backhaul. In someimplementations, base station 210 may include a network controller, aself-organizing network (SON) module or component, or a similar moduleor component. In other words, a base station 210 may perform networkcontrol, scheduling, and/or network management functions (e.g., forother base stations 210 and/or for uplink, downlink, and/or side linkcommunications of UEs 205 covered by the base station 210). In someimplementations, base station 210 may include a central unit andmultiple distributed units. The central unit may coordinate accesscontrol and communication with regard to the multiple distributed units.The multiple distributed units may provide UEs 205 and/or other basestations 210 with access to network 245.

In some implementations, base station 210 may provide a connectionrequest associated with a UE 205 to MME 215. In some implementations,base station 210 may receive a connection response associated with theUE 205 from MME 215. In some implementations, base station 210 mayreceive a response (e.g., a modify bearer response) from MME 215. Theresponse may include data usage information that may allow UE 205 tohave access to expected data usage permissions or expanded data usagepermissions.

MME 215 includes one or more devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with UE 205. In someimplementations, MME 215 may perform operations relating toauthentication of UE 205. Additionally, or alternatively, MME 215 mayfacilitate the selection of a particular SGW 220 and/or a particular PGW225 to serve traffic to and/or from UE 205. MME 215 may performoperations associated with handing off UE 205 from a first base station210 to a second base station 210 when UE 205 is transitioning from afirst cell associated with the first base station 210 to a second cellassociated with the second base station 210. Additionally, oralternatively, MME 215 may select another MME (not pictured), to whichUE 205 should be handed off (e.g., when UE 205 moves out of range of MME215).

In some implementations, MME 215 may be configured with a field that iscapable of defining a coverage area. In some implementations, a set ofindicator values associated with a set of base stations 210 may beincluded as values of the field. In some implementations, MME 215 mayreceive instructions to update the field that defines the coverage area(e.g., by adding identifiers to the field, by clearing the field, and/orthe like). In some implementations, MME 215 may support or have accessto a data structure that associates device identifiers of UEs 205 andparticular identifiers that identify users as being eligible to receiveexpanded data usage permissions. In some implementations, MME 215 mayprovide a request (e.g., a modify bearer request) to PCRF 230 (e.g.,directly, using one or more other network devices as intermediaries,etc.). In some implementations, MME 215 may receive a response (e.g., amodify bearer response) from PCRF 230 (e.g., directly, using one or moreother network devices as intermediaries, etc.).

SGW 220 includes one or more devices capable of routing packets. Forexample, SGW 220 may include one or more data processing and/or traffictransfer devices, such as a gateway, a router, a modem, a switch, afirewall, a network interface card (NIC), a hub, a bridge, a serverdevice, an optical add/drop multiplexer (OADM), or any other type ofdevice that processes and/or transfers traffic. In some implementations,SGW 220 may aggregate traffic received from one or more base stations210 associated with the LTE network and may send the aggregated trafficto network 245 (e.g., via PGW 225) and/or other network devicesassociated with the EPC and/or the IMS core. SGW 220 may also receivetraffic from network 245 and/or other network devices and may send thereceived traffic to UE 205 via base station 210. Additionally, oralternatively, SGW 220 may perform operations associated with handingoff UE 205 to and/or from an LTE network.

PGW 225 includes one or more devices capable of providing connectivityfor UE 205 to external packet data networks (e.g., other than thedepicted EPC and/or LTE network). For example, PGW 225 may include oneor more data processing and/or traffic transfer devices, such as agateway, a router, a modem, a switch, a firewall, a NIC, a hub, abridge, a server device, an OADM, or any other type of device thatprocesses and/or transfers traffic. In some implementations, PGW 225 mayaggregate traffic received from one or more SGWs 220 and may send theaggregated traffic to network 245. Additionally, or alternatively, PGW225 may receive traffic from network 245, and may send the traffic to UE205 via SGW 220 and base station 210. PGW 225 may record data usageinformation (e.g., byte usage), and may provide the data usageinformation to AAA 240.

PCRF 230 includes one or more network devices or other types ofcommunication devices. PCRF 230 may store subscriber information, suchas voice call and data rate plans or quotas for subscribers. In somecases, PCRF 230 may store, as part of the subscriber information, aparticular identifier that is used to identify a user as being eligibleto receive expanded data usage permissions. PCRF 230 may provide networkcontrol regarding service data flow detection, gating, Quality ofService (QoS), and/or flow-based charging. Policies and rules regardingQoS may include policies and rules instructing UE 205 and/or networkelements (base station 210, SGW 220, PGW 225, etc.) to minimize packetloss, to implement a packet delay budget, to provide a guaranteed bitrate (GBR), to provide a particular latency, to reduce RF signalcongestion, and/or to perform other activities associated with QoS. PCRF230 may provide policies and rules to other network devices, such asbase station 210, SGW 220, PGW 225, and/or the like, to implementnetwork control. PCRF 230 may determine how a certain service data flowshall be treated and may ensure that subscriber plane traffic mappingand QoS is in accordance with a subscriber's profile and/or networkpolicies.

HSS/SDM 235 includes one or more devices, such as one or more serverdevices, capable of managing (e.g., receiving, generating, storing,processing, and/or providing) information associated with UE 205. Forexample, HSS/SDM 235 may manage subscription information associated withUE 205, such as information that identifies a subscriber profile of auser associated with UE 205 (e.g., which may include a particularidentifier that identifies a user as eligible for expanded data usagepermissions), information that identifies services and/or applicationsthat are accessible to UE 205, location information associated with UE205, a network identifier (e.g., a network address) that identifies UE205, information that identifies a treatment of UE 205 (e.g., quality ofservice information, a quantity of minutes allowed per time period, aquantity of data consumption allowed per time period, etc.), and/orsimilar information. HSS/SDM 235 may provide this information to one ormore other devices of environment 200 to support the operationsperformed by those devices. In some implementations, HSS/SDM 235 mayserve as a single, virtual data store with a centralized administration,management, and/or reporting.

AAA 240 includes one or more devices, such as one or more serverdevices, that perform authentication, authorization, and/or accountingoperations for communication sessions associated with UE 205. Forexample, AAA 240 may perform authentication operations for UE 205 and/ora user of UE 205 (e.g., using one or more credentials), may controlaccess, by UE 205, to a service and/or an application (e.g., based onone or more restrictions, such as time-of-day restrictions, locationrestrictions, single or multiple access restrictions, read/writerestrictions, etc.), may track resources consumed by UE 205 (e.g., aquantity of voice minutes consumed, a quantity of data consumed, etc.),and/or may perform similar operations.

Network 245 includes one or more wired and/or wireless networks. Forexample, network 245 may include a cellular network (e.g., a 5G network,a 4G network, such as an LTE network, a 3G network, a code divisionmultiple access (CDMA) network, etc.), a public land mobile network(PLMN), a wireless local area network (e.g., a Wi-Fi network), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, and/ora combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to UE 205, base station 210, MME 215, SGW 220, PGW 225,PCRF 230, HSS/SDM 235, and/or AAA 240. In some implementations UE 205,base station 210, MME 215, SGW 220, PGW 225, PCRF 230, HSS/SDM 235,and/or AAA 240 may include one or more devices 300 and/or one or morecomponents of device 300. As shown in FIG. 3, device 300 may include abus 310, a processor 320, a memory 330, a storage component 340, aninput component 350, an output component 360, and a communicationinterface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a wireless local area network interface, a cellularnetwork interface, or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a diagram of an example functional architecture of a corenetwork 400 in which systems and/or methods, described herein, may beimplemented. For example, FIG. 4 may show an example architecture of a5G NG core network included in a 5G wireless telecommunications system.In some implementations, the example architecture may be implemented bya core network (e.g., a core network described with respect to FIG. 5)and/or one or more of devices (e.g., a device associated with FIG. 2 orFIG. 3). While the example architecture of shown in FIG. 4 may be anexample of a service-based architecture, in some implementations, theexample architecture may be implemented as a reference-pointarchitecture.

As shown in FIG. 4, core network 400 may include a number of functionalelements. The functional elements may include, for example, a networkslice selection function (NSSF) 402, a network exposure function (NEF)404, an authentication server function (AUSF) 406, a unified datamanagement (UDM) component 408, a policy control function (PCF) 410, anapplication function (AF) 412, an access and mobility managementfunction (AMF) 414, a session management function (SMF) 416, a userplane function (UPF) 418, a data network 420, and/or the like. Thesefunctional elements may be communicatively connected via a message bus422. Each of the functional elements shown in FIG. 4 is implemented onone or more devices associated with a wireless telecommunicationssystem. In some implementations, one or more of the functional elementsmay be implemented on physical devices, such as an access point, a basestation, a gateway, and/or the like. In some implementations, one ormore of the functional elements may be implemented on a computing deviceof a cloud computing environment.

NSSF 402 is a hardware-based element that may select network sliceinstances for UEs (and/or may determine network slice policies to beapplied at a RAN). By providing network slicing, NSSF 402 allows anoperator to deploy multiple substantially independent end-to-endnetworks potentially with the same infrastructure. In someimplementations, each slice may be customized for different services.NEF 404 is a hardware-based element that may support the exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services.

AUSF 406 is a hardware-based element that may act as an authenticationserver and support the process of authenticating UEs in the wirelesstelecommunications system. UDM component 408 is a hardware-based elementthat may store subscriber data and profiles in the wirelesstelecommunications system. UDM component 408 may be used for fixedaccess, mobile access, and/or the like, in core network 400. In someimplementations, UDM component 408 may perform one or more functionsand/or features described as being performed by HSS/SDM 235. PCF 410 isa hardware-based element that may provide a policy framework thatincorporates network slicing, roaming, packet processing, mobilitymanagement, and/or the like. In some implementations, PCF 410 mayperform one or more functions and/or features described as beingperformed by PCRF 230.

AF 412 is a hardware-based element that may support applicationinfluence on traffic routing, access to NEF 404, policy control, and/orthe like. AMF 414 is a hardware-based element that may act as atermination point for Non Access Stratum (NAS) signaling, mobilitymanagement, and/or the like. In some implementations, AMF 414 mayperform one or more functions and/or features described as beingperformed by a mobility management entity (MME). For example, AMF 414may perform a set of actions that provide a UE with expanded data usagepermissions, in a same or similar manner as that described elsewhereherein. SMF 416 is a hardware-based element that may support theestablishment, modification, and release of communications sessions inthe wireless telecommunications system. For example, SMF 416 mayconfigure traffic steering policies at UPF 418, enforce UE IP addressallocation and policies, and/or the like.

UPF 418 is a hardware-based element that may serve as an anchor pointfor intra/inter-Radio Access Technology (RAT) mobility. UPF 418 mayapply rules to packets, such as rules pertaining to packet routing,traffic reporting, handling user plane QoS, and/or the like. Datanetwork 420 may include various types of data networks, such as theInternet, a third party services network, an operator services network,a private network, a wide area network, and/or the like. Message bus 422represents a communication structure for communication among thefunctional elements. In other words, message bus 422 may permitcommunication between two or more functional elements.

The number and arrangement of functional elements shown in FIG. 4 areprovided as an example. In practice, there may be additional functionalelements, fewer functional elements, different functional elements, ordifferently arranged functional elements than those shown in FIG. 4.Furthermore, two or more functional elements shown in FIG. 4 may beimplemented within a single device, or a single functional element shownin FIG. 4 may be implemented as multiple, distributed devices.Additionally, or alternatively, a set of functional elements (e.g., oneor more functional elements) of core network 400 may perform one or morefunctions described as being performed by another set of functionalelements of core network 400.

FIG. 5 is a diagram of an example environment 500 in which systems,functional elements, and/or methods, described herein, may beimplemented. As shown in FIG. 5, environment 500 may include one or moreUEs 510, one or more base stations 520, a core network 530, and/or oneor more data networks 540. Devices of environment 500 may interconnectvia wired connections, wireless connections, or a combination of wiredand wireless connections.

UE 510 includes one or more devices capable of communicating with basestation 520 and/or data network 540 (e.g., via core network 530). Forexample, UE 510 may include a wireless communications device, aradiotelephone, a personal communications system (PCS) terminal (e.g.,that may combine a cellular radiotelephone with data processing and datacommunications capabilities), a smart phone, a laptop computer, a tabletcomputer, a personal gaming system, a mobile hotspot device, a fixedwireless access device, a customer premises equipment, and/or a similardevice. UE 510 may be capable of communicating using uplink (e.g., UE510 to base station 520) communications, downlink (e.g., base station520 to UE 510) communications, and/or sidelink (e.g., UE-to-UE)communications. In some implementations, UE 510 may include amachine-type communication (MTC) UE, such as an evolved or enhanced MTC(eMTC) UE. In some implementations, UE 510 may include an Internet ofThings (IoT) UE, such as a narrowband IoT (NB-IoT) UE and/or the like.In some implementations, UE 510 may be capable of communicating usingmultiple RATs.

Base station 520 includes one or more devices capable of communicatingwith UE 510 using a cellular RAT. For example, base station 520 mayinclude a base transceiver station, a radio base station, a node B, aneNB, a gNB, a base station subsystem, a cellular site, a cellular tower(e.g., a cell phone tower, a mobile phone tower, and/or the like), anaccess point, a transmit receive point (TRP), a radio access node, amacrocell base station, a microcell base station, a picocell basestation, a femtocell base station, or a similar type of device. Basestation 520 may transfer traffic between UE 510 (e.g., using a cellularRAT), other base stations 520 (e.g., using a wireless interface or abackhaul interface, such as a wired backhaul interface), and/or corenetwork 530. Base station 520 may provide one or more cells that covergeographic areas. Some base stations 520 may be mobile base stations.Some base stations 520 may be capable of communicating using multipleRATs.

In some implementations, base station 520 may perform scheduling and/orresource management for UEs 510 covered by base station 520 (e.g., UEs510 covered by a cell provided by base station 520). In someimplementations, base stations 520 may be controlled or coordinated by anetwork controller, which may perform load balancing, network-levelconfiguration, and/or the like. The network controller may communicatewith base stations 520 via a wireless or wireline backhaul. In someimplementations, base station 520 may include a network controller, aself-organizing network (SON) module or component, or a similar moduleor component. In other words, a base station 520 may perform networkcontrol, scheduling, and/or network management functions (e.g., forother base stations 520 and/or for uplink, downlink, and/or sidelinkcommunications of UEs 510 covered by the base station 520). In someimplementations, base station 520 may include a central unit andmultiple distributed units. The central unit may coordinate accesscontrol and communication with regard to the multiple distributed units.The multiple distributed units may provide UEs 510 and/or other basestations 520 with access to data network 540 via core network 530.

Core network 530 includes various types of core network architectures,such as a 5G NG Core (e.g., a core network capable of being utilized byUPF 418 or other devices or components associated with FIG. 5), along-term evolution (LTE) evolved packet core (EPC), and/or the like. Insome implementations, core network 530 may be implemented on physicaldevices, such as a gateway, a mobility management entity, and/or thelike. In some implementations, the hardware and/or software implementingcore network 530 may be virtualized (e.g., through the use of networkfunction virtualization and/or software-defined networking), therebyallowing for the use of composable infrastructure when implementing corenetwork 530. In this way, networking, storage, and compute resources maybe allocated to implement the functions of core network 530 (describedin FIG. 5) in a flexible manner as opposed to relying on dedicatedhardware and software to implement these functions.

Data network 540 includes one or more wired and/or wireless datanetworks. For example, data network 540 may include an IMS, a publicland mobile network (PLMN), a local area network (LAN), a wide areanetwork (WAN), a metropolitan area network (MAN), a private network suchas a corporate intranet, an ad hoc network, the Internet, a fiberoptic-based network, a cloud computing network, a third party servicesnetwork, an operator services network, and/or the like, and/or acombination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 5 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 5. Furthermore, two or more devices shown in FIG. 5 may beimplemented within a single device, or a single device shown in FIG. 5may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 500 may perform one or more functions described as beingperformed by another set of devices of environment 500.

FIG. 6 is a flow chart of an example process 600 for providing a userequipment (UE) that is within a coverage area with expanded data usagepermissions. In some implementations, one or more process blocks of FIG.6 may be performed by a mobility management entity (MME) (e.g., MME215). In some implementations, one or more process blocks of FIG. 6 maybe performed by another device or a group of devices separate from orincluding the MME, such as a user equipment (UE) (e.g., UE 205), a basestation (e.g., base station 210), a serving gateway (SGW) (e.g., SGW220), a packet data network gateway (PGW) (e.g., PGW 225), a policy andcharging rules function (PCRF) (e.g., PCRF 230), a home subscriberserver/subscriber data manager (HSS/SDM) (e.g., HSS/SDM 235), anauthentication, authorization, and account server (AAA) (e.g., AAA 240),and/or one or more devices described in connection with FIGS. 4 and 5.

As shown in FIG. 6, process 600 may include receiving instructions toupdate one or more fields that define a coverage area within a network,wherein the coverage area is to be used to grant a set of user equipment(UEs) with access to expanded data usage permissions (block 610). Forexample, the MME (e.g., using processor 320, memory 330, input component350, communication interface 370, and/or the like) may receiveinstructions to update one or more fields that define a coverage areawithin a network, as described above. In some implementations, thecoverage area may be used to grant a set of user equipment (UEs) withaccess to expanded data usage permissions.

In some implementations, before receiving the instructions to update theone or more fields, the MME may receive a connection request for the UEto connect to the network. In some cases, the MME may obtain, from theother device, particular account information associated with the UE,that includes a particular identifier of the one or more particularidentifiers. Additionally, the MME may analyze the account informationto identify the particular identifier. Next, the MME may update a datastructure to associate a device identifier of the UE and the particularidentifier. Furthermore, the MME may determine that the coverage area isnot active by analyzing the one or more fields. Additionally, the MMEmay cause, before receiving the instructions to update the one or morefields, the UE to connect to the network with data usage permissions.The data usage permissions may be data usage permissions expected by theuser, data usage permissions identified in a data plan of the user,and/or the like.

In some implementations, before receiving the instructions to update theone or more fields and based on an event, the MME may cause the accountinformation for the one or more users to include the one or moreparticular identifiers. The event may include an incident causing agroup of first responders to enter the coverage area, and/or a serviceoutage in at least a portion of the coverage area.

As further shown in FIG. 6, process 600 may include updating, based onreceiving the instructions, the one or more fields to include a set ofidentifiers that are associated with a group of base stations within thecoverage area (block 620). For example, the MME (e.g., using processor320, memory 330, storage component 340, and/or the like) may update,based on receiving the instructions, the one or more fields to include aset of identifiers that are associated with a group of base stationswithin the coverage area, as described above.

In some implementations, after updating the one or more fields, the MMEmay receive a connection request for the UE to connect to the network.Additionally, the MME may obtain, from the other device, the accountinformation that includes the particular identifier. Next, the MME mayanalyze the account information to identify the particular identifier.Furthermore, the MME may update a data structure to associate a deviceidentifier of the UE and the particular identifier. In some cases, theMME may determine whether the coverage area is active by analyzing theone or more fields that have been updated.

As further shown in FIG. 6, process 600 may include determining that aUE, that is connected to the network, qualifies for the expanded datausage permissions, wherein the UE qualifies for the expanded data usagepermissions based on account information associated with the UEincluding a particular identifier that allows the UE to utilize theexpanded data usage permissions (block 630). For example, the MME (e.g.,using processor 320, memory 330, storage component 340, and/or the like)may determine that a UE, that is connected to the network, qualifies forthe expanded data usage permissions, as described above. In someimplementations, the UE may qualify for the expanded data usagepermissions based on account information associated with the UEincluding a particular identifier that allows the UE to utilize theexpanded data usage permissions.

In some implementations, when determining that the UE qualifies for theexpanded data usage permissions, the MME may use a device identifier ofthe UE to search a data structure that associates a corresponding deviceidentifier with the particular identifier. In some implementations, whendetermining that the UE qualifies for the expanded data usagepermissions, the MME may provide the device identifier to the otherdevice to cause the other device to verify that the particularidentifier is included in the account information associated with the UEand to provide an indication that the UE qualifies for the expanded datausage permissions to the device. In some implementations, whendetermining that the UE qualifies for the expanded data usagepermissions, the MME may obtain the account information from the otherdevice and process may the account information to determine whether theaccount information includes the particular identifier.

As further shown in FIG. 6, process 600 may include providing, toanother device, a request for data usage information that reflects theexpanded data usage permissions (block 640). For example, the MME (e.g.,using processor 320, memory 330, output component 360, communicationinterface 370, and/or the like) may provide, to another device (e.g.,the PCRF), a request (e.g., a modify bearer request) for data usageinformation that reflects the expanded data usage permissions, asdescribed above.

In some implementations, when providing the request, the MME may providethe request based on determining that the account information includesthe particular identifier and based on determining that the coveragearea is active. For example, this may occur in situations where the UEconnections to the network after the coverage area has been activated.

In some implementations, the MME may receive, from the other device, aresponse that includes the data usage information that reflects theexpanded data usage permissions. For example, the MME may receive amodify bearer response from the PCRF that includes the data usageinformation that reflects the expanded data usage permissions.

As further shown in FIG. 6, process 600 may include causing the datausage information to be applied to a session associated with the UE(block 650). For example, the MME (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may cause the data usageinformation to be applied to a session associated with the UE, asdescribed above. As a particular example, the MME may provide the datausage information to one or more serving base stations to allow the datausage information to be applied to one or more sessions associated withthe one or more UEs.

In some implementations, applying the data usage information to thesession provides the UE with access to a quantity of data that isgreater than a particular quantity of data identified in a data plan ofthe user, access to the data in a manner that is free of cost, access tothe data in a manner that causes data usage to be unaffected by one ormore quality of service (QoS) service restrictions identified in thedata plan of the user, and/or access to the data in a manner thatremoves one or more data throttling restrictions.

In some implementations, the account information may include informationidentifying a billing postal code that is outside of the coverage area.In some implementations, the MME may cause the session to be establishedto allow the UE to access data in a manner indicated by the data usageinformation.

In some implementations, the MME may receive particular instructions toreset at least one value of at least one of the one or more fields thatdefine the coverage area. For example, the MME may reset the one or morefields by updating the one or more fields to include null values.Additionally, the MME may provide, to the other device, a new requestfor particular data usage information that reflects data usagepermissions. The data usage permissions may be based on a data plan ofthe user. Furthermore, the MME may receive, from the other device, theparticular data usage information, and may cause the particular datausage information to be applied to the session associated with the UE.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc., depending onthe context.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the phrase “only one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device,instructions to update one or more fields that define a coverage areawithin a network, wherein the coverage area is to be used to grant a setof user equipment (UEs) with access to expanded data usage permissions;updating, by the device and based on receiving the instructions, the oneor more fields to include a set of identifiers that are associated witha group of base stations within the coverage area; determining, by thedevice, that a UE, that is connected to the network, qualifies for theexpanded data usage permissions, wherein the UE qualifies for theexpanded data usage permissions based on account information of anaccount associated with the UE including a particular identifier thatallows the UE to utilize the expanded data usage permissions; providing,by the device and to another device, a request for data usageinformation that reflects the expanded data usage permissions; andcausing, by the device, the data usage information to be applied to asession associated with the UE.
 2. The method of claim 1, whereinapplying the data usage information to the session provides the UE withat least one of: access a quantity of data that is greater than aparticular quantity of data identified in a data plan of the user,access to the data in a manner that is free of cost, access to the datain a manner that causes data usage to be unaffected by one or morequality of service (QoS) service restrictions identified in the dataplan of the user, or access to the data in a manner that removes datathrottling limitations.
 3. The method of claim 1, wherein the accountinformation includes information identifying a billing postal code thatis outside of the coverage area.
 4. The method of claim 1, whereindetermining that the UE qualifies for the expanded data usagepermissions comprises: using a device identifier of the UE to search adata structure that associates a corresponding device identifier withthe particular identifier that allows the UE to utilize the expandeddata usage permissions, or providing the device identifier to the otherdevice to cause the other device to verify that the particularidentifier is included in the account information associated with the UEand to provide an indication that the UE qualifies for the expanded datausage permissions to the device.
 5. The method of claim 1, furthercomprising: receiving a connection request for the UE to connect to thenetwork; obtaining, from the other device, the account information thatincludes the particular identifier; analyzing the account information toidentify the particular identifier; updating a data structure toassociate a device identifier of the UE and the particular identifier;determining that the coverage area is not active by analyzing the one ormore fields; and causing, before receiving the instructions to updatethe one or more fields, the UE to connect to the network with data usagepermissions that are based on a data plan of the user.
 6. The method ofclaim 1, further comprising: receiving, after updating the one or morefields, a connection request for the UE to connect to the network;obtaining, from the other device, the account information that includesthe particular identifier; analyzing the account information to identifythe particular identifier; updating a data structure to associate adevice identifier of the UE and the particular identifier; determiningthat the coverage area is active by analyzing the one or more fieldsthat have been updated; and wherein providing the request comprises:providing the request based on determining that the account informationincludes the particular identifier and based on determining that thecoverage area is active.
 7. The method of claim 1, further comprising:receiving particular instructions to reset the one or more fields thatdefine the coverage area; updating the one or more fields to includenull values; providing, to the other device, a new request forparticular data usage information that reflects data usage permissions,wherein the data usage permissions are based on a data plan of the user;receiving, from the other device, the particular data usage information;and causing the particular data usage information to be applied to thesession associated with the UE.
 8. A device, comprising: one or morememories; and one or more processors, operatively coupled to the one ormore memories, configured to: receive instructions to update one or morefields that define a coverage area within a network, wherein thecoverage area is to be used to grant access to expanded data usagepermissions; update, based on receiving the instructions, the one ormore fields to include a set of identifiers that are associated with agroup of base stations within the coverage area; determine that one ormore user equipment (UEs), that are connected to the network, qualifyfor the expanded data usage permissions, wherein the one or more UEsqualify for the expanded data usage permissions based on accountinformation, for one or more users that are associated with the one ormore UEs, including one or more particular identifiers that allow theone or more UEs to utilize the expanded data usage permissions; provide,to another device, a request for data usage information for the one ormore UEs that reflect the expanded data usage permissions, wherein therequest includes one or more device identifiers for the one or more UEs;receive, from the other device, a response that includes the data usageinformation; and provide the data usage information to one or moreserving base stations to allow the data usage information to be appliedto one or more sessions associated with the one or more UEs.
 9. Thedevice of claim 8, wherein the one or more processors, when updating theone or more fields, are configured to: update the one or more fieldsbased on an event.
 10. The device of claim 8, wherein applying the datausage information to the one or more sessions provides the one or moreUEs with access to at least one of: access a quantity of data that isgreater than a particular quantity of data identified in a data plan ofthe user, access to the data in a manner that is free of cost, access tothe data in a manner that is not affected by one or more quality ofservice (QoS) service restrictions identified in the data plan of theuser, or access to the data in a manner that removes data throttlinglimitations.
 11. The device of claim 8, wherein the one or moreprocessors, when determining that a UE, of the one or more UEs,qualifies for the expanded data usage permissions, are configured to:use a device identifier of the UE to search a data structure thatassociates a corresponding device identifier with a particularidentifier of the one or more particular identifiers, or provide thedevice identifier to the other device to cause the other device toverify that the particular identifier is included in the accountinformation associated with the UE and to provide an indication that theUE qualifies for the expanded data usage permissions to the device. 12.The device of claim 8, wherein the one or more processors are furtherconfigured to: receive, before receiving the instructions to update theone or more fields, a connection request for a UE, of the one or moreUEs, to connect to the network; obtain, from the other device,particular account information for a user associated with the UE, thatincludes a particular identifier of the one or more particularidentifiers; analyze the particular account information to identify theparticular identifier; update a data structure to associate a deviceidentifier of the UE and the particular identifier; determine that thecoverage area is not active by analyzing the one or more fields; andcause, before receiving the instructions to update the one or morefields, the UE to connect to the network without the expanded data usagepermissions.
 13. The device of claim 8, wherein the one or moreprocessors are further configured to: receive, after updating the one ormore fields, a connection request for a UE, of the one or more UEs, toconnect to the network; obtain, from the other device and for a userassociated with the UE, particular account information that includes aparticular identifier of the one or more particular identifiers; analyzethe particular account information to identify the particularidentifier; update a data structure to associate a device identifier ofthe UE and the particular identifier; determine that the coverage areais active by analyzing the one or more fields that have been updated;wherein the one or more processors, when providing the request, are to:provide, to the other device, a modify bearer request associated withthe UE, based on determining that the particular account informationincludes the particular identifier, and based on determining that thecoverage area is active; and wherein the one or more processors, whencausing the data usage information to be applied to the one or moresessions, are to: cause a session associated with the UE to beestablished to allow the UE to access data in a manner indicated by thedata usage information.
 14. The device of claim 8, wherein the one ormore processors are further configured to: receive particularinstructions to reset at least one of the one or more fields of thecoverage area, wherein the reset is to cause at least a portion of thecoverage area to no longer provide the expanded data usage permissions;update at least one of the one or more fields to include a null value;provide, to the other device, a new request for particular data usageinformation that reflects data usage permissions, wherein the newrequest applies to particular UEs that are in the portion of thecoverage area that is to no longer provide the expanded data usagepermissions; receive, from the other device, the particular data usageinformation; and cause the particular data usage information to beapplied to sessions associated with the particular UEs.
 15. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors of a device, cause the one or more processors to:receive instructions to update one or more fields that define a coveragearea within a network, wherein the coverage area is to be used to granta set of user equipment (UEs) with access to expanded data usagepermissions; update, based on receiving the instructions, the one ormore fields to include a set of identifiers that are associated with agroup of base stations within the coverage area; receive a connectionrequest for a UE to connect to the network; determine that the UEqualifies for the expanded data usage permissions based on accountinformation associated with the UE including a particular identifierthat allows the UE to utilize the expanded data usage permissions;obtain data usage information that reflects the expanded data usagepermissions; and cause a session to be established for the UE in amanner that applies the data usage information.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the instructions to updatethe one or more fields are received based on an event, and wherein theevent includes at least one of: an incident causing a group of firstresponders to enter the coverage area, or a service outage in at least aportion of the coverage area.
 17. The non-transitory computer-readablemedium of claim 15, wherein the account information includes informationidentifying a billing postal code that is outside of the coverage area.18. The non-transitory computer-readable medium of claim 15, whereinapplying the data usage information to the session provides the UE withaccess to at least one of: access a quantity of data that is greaterthan a particular quantity of data identified in a data plan of theuser, access to the data in a manner that is free of cost, access to thedata in a manner that is not affected by one or more quality of service(QoS) service restrictions identified in the data plan of the user, oraccess to the data in a manner that removes data throttling limitations.19. The non-transitory computer-readable medium of claim 15, wherein theone or more instructions, that cause the one or more processors todetermine that the UE qualifies for the expanded data usage permissions,cause the one or more processors to: provide the device identifier ofthe UE to another device to cause the other device to verify that theparticular identifier is included in the account information associatedwith the UE and to provide an indication that the UE qualifies for theexpanded data usage permissions to the device, or obtain the accountinformation from the other device and process the account information todetermine whether the account information includes the particularidentifier.
 20. The non-transitory computer-readable medium of claim 15,wherein the one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: receiveparticular instructions to reset the one or more fields that define thecoverage area; update the one or more fields to include null values;obtain particular data usage information that reflects data usagepermissions that are based on a data plan of the user; and cause theparticular data usage information to be applied to the sessionassociated with the UE.